-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make the Makefile build fully customizable #113
Conversation
Codecov ReportBase: 33.93% // Head: 33.93% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## main #113 +/- ##
=======================================
Coverage 33.93% 33.93%
=======================================
Files 42 42
Lines 8080 8080
=======================================
Hits 2742 2742
Misses 5121 5121
Partials 217 217
Flags with carried forward coverage won't be shown. Click here to find out more. Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
ed7f765
to
296d27c
Compare
f23cd8a
to
0ab4a00
Compare
0ab4a00
to
71b3090
Compare
7506ffe
to
6da8cf7
Compare
cec0f7f
to
12f9f5d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. The only questionable part (from my POV) is the use of shell which docker
versus shell which podman
. I would prefer to have Podman as default but I am not going to block the PR on this.
12f9f5d
to
1184755
Compare
1184755
to
2ef21e7
Compare
2ef21e7
to
6151414
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, just one comment about setting CONTAINER_CMD in .bazelrc
.bazelrc
Outdated
@@ -1,3 +1,6 @@ | |||
# Container Runtime | |||
build --action_env=CONTAINER_CMD=/usr/bin/docker |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why do we need to set this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In case both docker and podman are installed this is used to force the use of one of them. This could be useful to test builds with both container runtimes without having to remove podman to test docker.
6151414
to
f5a997e
Compare
215d528
to
84b8498
Compare
84b8498
to
0b39ecb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
minor comment about indentation, other than that - lgtm
@mnecas can you please take a look at the operator part?
8ef8e02
to
99c3470
Compare
99c3470
to
4a0e3db
Compare
Prefer `podman` over `docker`. Make the build fully customizable through environment variables. Use `CONTROLLER_GEN` var to specify which `controller-gen` binary must be used and make sure the correct version is installed when using the default one. Make consistent use of parentheses instead of curly braces for variable delimitation. Add sandbox writeable paths, needed after `bazel clean`. Signed-off-by: Miguel Martín <mmartinv@redhat.com>
4a0e3db
to
612269a
Compare
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
podman
overdocker
in Makefile buildsvariables.
CONTROLLER_GEN
var to specify whichcontroller-gen
binary must be used and make sure the correct version is
installed when using the default one.
for variable delimitation.
bazel clean
.